From: Richard M. Stallman Date: Mon, 13 Oct 2003 19:28:44 +0000 (+0000) Subject: (Parsing Expressions): Clean up forward-comment X-Git-Tag: archive/raspbian/1%29.2+1-2+rpi1~1^2~25210 X-Git-Url: https://dgit.raspbian.org/%22http:/www.example.com/cgi/%22https:/www.github.com/%22bookmarks:///%22http:/www.example.com/cgi/%22https:/www.github.com/%22bookmarks:/?a=commitdiff_plain;h=f3d4f8f1205915cbd1fa907e9c4d9ec7f77e4444;p=emacs.git (Parsing Expressions): Clean up forward-comment and parse-sexp-lookup-properties. --- diff --git a/lispref/syntax.texi b/lispref/syntax.texi index 217e0ccbd67..7bf67d1f257 100644 --- a/lispref/syntax.texi +++ b/lispref/syntax.texi @@ -771,7 +771,7 @@ end of a comment. This limitation no longer exists. @vindex parse-sexp-lookup-properties The behaviour of @code{parse-partial-sexp} is also affected by -@code{parse-sexp-lookup-properties} @xref{Syntax Properties}. +@code{parse-sexp-lookup-properties} (@pxref{Syntax Properties}). You can use @code{forward-comment} to move forward or backward over one comment or several comments. @@ -786,8 +786,8 @@ place where it stopped. This includes (for instance) finding the end of a comment when moving forward and expecting the beginning of one. The function also stops immediately after moving over the specified number of complete comments. If @var{count} comments are found as -expected, with nothing except whitespace between them, return -@code{t}; otherwise return @code{nil}. +expected, with nothing except whitespace between them, it returns +@code{t}; otherwise it returns @code{nil}. This function cannot tell whether the ``comments'' it traverses are embedded within a string. If they look like comments, it treats them